home *** CD-ROM | disk | FTP | other *** search
- There's a bit of confusion and a lot of bug reports regarding iptables
- commands and kernel support. Basically, any given extension has kernel
- code and a complimentary userspace module to configure it.
-
- Without the kernel support, you get errors like this:
-
- ## example from http://www.securityfocus.com/infocus/1723
- # iptables -A INPUT -p tcp -m tcp --dport 135 -j TARPIT
- iptables: No chain/target/match by that name
-
- In that example, TARPIT is not available in the kernel.
-
- Without the userspace support, you get errors like this:
-
- # iptables -A INPUT -p tcp --dport 80 -j FOO
- iptables v1.4.0: Couldn't load target `FOO':/lib/iptables/libipt_FOO.so: cannot open shared object file: No such file or directory
-
- Try `iptables -h' or 'iptables --help' for more information.
-
- In that example, the iptables extension FOO does not exist.
-
- Basically, the iptables package has support for extensions that
- might not be enabled in your kernel. Some of the extensions
- (specifically: u32, set, TARPIT, IPV4OPTSSTRIP and ipv4options) are
- from patch-o-matic-ng at the netfilter ftp site. Various versions
- of the kernel code is currently available there and in Debian's
- netfilter-extensions-source package. Other extensions may only be
- available with certain kernel versions. Your mileage may vary on
- adding kernel extensions.
-